System Options

Defines the company name that is hard coded into the Deacom system license file.

• If the company name is misspelled or needs to be changed, refer to the Overview section.
• Company name and address information entered on this tab will print on default reports unless user reports are created and modified.

Company address information that will be used on reports in the system.

Company phone and fax number that will be used on reports in the system.

Search field used to select a Country Code applicable to the phone number defined.

Remit to company name that will be used on reports in the system. If the Remit To information is same as the Company information, leave the entire set of Remit To field names blank.

Text field used for EDI purposes and, in particular, when using SPS Commerce as the customer's VAN for EDI transactions.

• Specifically, this field is necessary when an Invoice is triggered on a Sales Order identifying an ID associated with the Remit To on the invoice
• This value would be preset on the Sales Order and returned on an invoice indicating where the customer should remit payments to.

Remit to address information that will be used on reports in the system.

• A valid two digit country code is required if using credit card processors.

Defines the default font name for the data displayed in grids.

• Font size can also be modified, and fonts may be configured to display in bold and/or italics.

Defines the font that will be used in all Memo boxes throughout the system. This is not the same as a default since the user cannot change the font on the fly in Memo fields. Useful in situations where User-Defined Memo fields need to match the font name and size on generated reports/print outs.

Defines the font size that will be used in all Memo boxes throughout the system. This is not the same as a default since the user cannot change the font size on the fly in Memo fields. Useful in situations where User-Defined Memo fields need to match the font name and size on generated reports/print outs.

Defines the default font size for data displayed in grids.

Defines the default background color for alternating rows of data displayed in grids.

Determines which engine the system will use to evaluate the various expressions used throughout the Deacom system. Options are Legacy and Scripting.

• For scripting, all available fields to an expression are available via the Fields object or the Globals object. For instance Globals.ordmask or Fields.pr_codenum. Related cursor fields are available via the cursor name, dot, and then the field name. This is the same as the classic expression engine. For instance: cUSERCALCS.u_calcname.
• Please reference the Scripting Backwards Compatibility Chart for detailed information on legacy functions and the scripting equivalent.
• Note: The system can be set to use the scripting engine in one-off scenarios by having the expression field start with "#Engine=Scripting" In this case, the system option could be set to "Legacy" and the scripting engine would be used only for those expressions that start with "#Engine=Scripting"

Controls how the "Save" button works when clicked on forms throughout the system. A save can be initiated via a mouse click or keyboard shortcut. Options are:

• Save - default. Information entered on the form is saved in the system.
• Save and Close - Information entered on the form is saved and form will be closed. Note that all securities related to the fields/form are validated. If a security or prompt prevents the save, the form will not be closed.

If checked, the cursor will default to the 'Search All Columns' field within a search box.

Defines the X margin, in millimeters, for the PDF printer.

• Allows users to specify the X margin outside of the default value.

Defines the Y margin, in millimeters, for the PDF printer.

• Allows users to specify the Y margin outside of the default value.

Memo field used to define the text which will be printed in the footer of Excel spreadsheets when data grids are exported from Deacom.

Memo field used to define the caption that will appear when e-mailing documents within Deacom. Signature will apply to all users.

Specifies the location of the logo file to be displayed in the web application.

• If the file selector does not work correctly, type the full path and file name into the field.
• This field is also used in Report Layouts to display the system logo. Rectangles objects within the toolbar design have a checkbox to use the system logo, and the image is loaded using this path.

Specifies the location of the default network directory for documents to be linked using the File/Import Documents function.

Days to retain documents, depending on the license. The default is 730 days.

Defines the maximum total size (in megabytes) allowed for all documents attached to a single master record in the system when using the "View Docs" button.

• Only available in the classic interface of Deacom, not in web based versions.
• Applies to all master records or transactions that contain the "View Docs" button, such as Sales Orders, Vendors, Parts, Journal Entries, etc.
• Example: If the value in this field is 10 and a user attempts to attach four files (of any type) that are each 3 MB, the user will be prevented form adding the fourth file.
• There is no option to specify additional parameters, such as specific file types or additional restrictions.

Pick list used to specify what DPI setting (150, 300, or 450) will be used when rendering/printing documents in Deacom.

• Higher settings should help in situations where scanning barcodes is inconsistent.
• This field is only available in web versions of Deacom.

Memo field used to define the file extensions that may be uploaded as attachments in the Deacom system. Disabling certain file extensions/types, such as html, can be useful to help prevent malicious activity.

• The field comes default with the following extensions: .ai, .bmp, .doc, .docx, .eps, .gif, .jpeg, .jpg, .odt, .pdf, .png, .ppt, .pptx, .rtf, .txt, .xls, .xlsx, .xml
• When uploading a document as an attached document, the system will check this field to see if any of the comma-separated file extensions match the file extension of the document being uploaded. If the attachment is not one of the allowable file extensions, the user will receive the following prompt: "This file type is not an allowable attached file type. Please contact your system administrator to add this file type to the allowable list."

Combobox that specifies how a printer is displayed in the main app and WMS. The options are as follows:

• Full Path - Default, displays the full UNC path of the printer as the name.
• Printer Name - Only displays the printer name/shared name. Useful for printers that are shared from a server to the web or automation service.

If checked, document control may be established in the system and document history (viewing and modifying documents) can be tracked in the system.

• Attempting to uncheck this field in situations where any Document Categories have the “E-Signature Required” flag checked will result in the following prompt: “Document history cannot be removed with existing document categories set to require E-Signatures”.

Defines the number of days before a password can be changed.

• If set to zero, passwords can be changed at any time.

Defines the number of days before a password must be changed.

• If set to zero, passwords are never forced to be changed.

Defines the minimum length a password must be.

• If the user tries to specify too short of a password, the system will prompt the user that the password must be longer.

Defines the number of times a password must be changed before a previously used password can be re-used.

Defines the number of days prior to a password expiring that a prompt appears letting users know the password must soon be changed.

Defines the number of days before a user is locked out of the system due to inactivity. When the user is locked out, the system administrator must unlock their user through System > Maintenance > Users.

Defines the number of minutes a mobile user can be inactive before they are logged out of the Deacom Mobile application.

If checked, new Users created will only be permitted to access one Deacom application (Cash Register, WMS, Mobile, DSD, Tracker, AutoFinisher, and Main App) at a time.

• If a user attempts to log in to an app while they are already logged into a different platform, they will be prompted with "You are already logged into <<Application Name>> and are only allowed to be logged into one application at a time. Do you want to continue with this login and terminate the other session?"

If checked, the "Approved Device Authentication" flag is checked by default on the user record when adding a new user to the system.

If checked, the "Email Authentication" flag is checked by default on the user record when adding a new user to the system.

Defines how many minutes the email code will be valid when using the Email Authentication option.

If checked, the "Security Question Authentication" flag is checked by default on the user record when adding a new user to the system.

Defines how many security questions a user must answer to successfully authenticate. Security questions are defined via System > Maintenance > Security Questions.

If checked, all User passwords must contain both letters and numbers.

If checked, all User passwords must contain at least one number.

If checked, all User passwords must contain at least one special character.

If checked, all User passwords must contain at least one uppercase letter.

If checked, Users may check the "Remember Password For Two Weeks" flag on the application login screen. Checking the "Remember Password For Two Weeks" flag will automatically log the user in when Deacom is opened, as long as the Deacom user credentials match the Windows user credentials on the computer accessing the system.

Defines the local network domain. Used in connection with the "LDAP User" field on the Edit User form to allow users the option of logging into Deacom applications (WMS, Cash Register etc.) using their network username and password.

Optional System Option for SSO Certificate to match against an incoming certificate. This protects against external tampering or replicating an Okta account.

• Required when the Single Sign-On Method is set to URL and using Azure for authenticating in the main application.

Defines the single sign on method (SSO) that will be used. Options are None (Default), CyberArk, Okta, URL.

• Companies will need to have create the appropriate Azure Active Directory account settings and credentials before using this option.
• Beginning in version 17.02.003 e-Signatures within Deacom are integrated and authenticated with the Okta SSO. If Okta is selected in this field, users will be prompted to enter their Okta credentials on any/all e-Signatures forms in the system. The prompt will read "Please enter your OKTA credentials". This supports 21 CRF Part 11 compliance.
• This field is unavailable if the "Access Deacom Restart" field (on the Edit User form) is checked.
• The URL option is used with Azure.

Defines how the single sign on method will be authenticated. Options are Username or Email.

• This field is only enabled when the "Single Sign-On Method" field above is set to Okta or CyberArk.

Defines the App ID. Optional field.

• Only enabled and required when the Single Sign-On Method is set to URL and using Azure.
• Companies will need to have create the appropriate Azure Active Directory account settings and credentials before using this option.

Defines the SSO URL.

• Only enabled and required when the Single Sign-On Method is set to URL.
• Companies will need to have create the appropriate Azure Active Directory account settings and credentials before using this option.

Defines the company's user name used to access Help.

• This field is case-sensitive.

Defines the SMTP server name used for the default email host.

• Example: mail.company.com

Defines the port for the default email host.

• Example: 25.

Defines the interval, in minutes, which the system will gather email correspondence when using the email monitoring feature.

• Once the interval time has elapsed, the system will search through the Inbox and Sent Items folders of each user for any emails available for gathering.

Defines the CRM Note Type that will be used when monitored emails are added to Contact Notes.

• A value must be entered in this field if using the email monitoring feature.

Defines the authentication type used when connecting to Office365. Options are Basic (aka User-Pass Authentication) and OAuth2. This field is set to Basic by default.

• If using the "OAuth2" option the "Outlook App ID" and "Outlook Tenant ID" fields below are required.
• If not using the "OAuth2" option, users must follow Microsoft's instructions in order to set their users up for SMTP Auth, allowing them to continue using their current email server.
• OAuth2 support is available for Trigger Emails. If this field is set to OAuth2 and sending an email using trigger credentials, the system will use OAuth2 to send the trigger email.
• The following URL may be helpful in validating your connection to see if any issues are Deacom related or MS Exchange issues: https://testconnectivity.microsoft.com/tests/O365EwsTask/input

Defines the Application and Tenant ID passwords which are supplied by Microsoft when companies register their application, Deacom in this instance, with their Office365 account.

Defines the Application and Tenant ID passwords which are supplied by Microsoft when companies register their application, Deacom in this instance, with their Office365 account.

Option to define a secret that can be used for OAuth2 authentication. The secret is provided based on settings in the Azure Admin portal. Additional information on OAuth2 authentication is available via Configuring and Sending Emails in Deacom.

• This field is not required, but is an additional option that can be used with Azure SSO authentication. If a secret is provided in this field, it will be used to perform the authentication process behind the scenes and users will not be prompted to enter their credentials to authenticate.

Defines the email address that the system will use to send trigger emails.

• Example: [email protected].

If checked, the system uses the currently logged in User's network credentials.

• Uncheck if users wish to use a specific username and password for Trigger generation, indicated by the "Trigger Username" and "Trigger Password" fields.
• Default credentials can only be used if everyone’s active directory account has access to send mail through the trigger mail address.
• Checking this flag will not work for the majority of setups, but the option is available and is similar to a Public Folders mail account.
• Example: If a test environment is created and all users' active directory accounts have the keys to Public Folders and the public folder was the trigger mail account, all users could send through it and therefore Triggers could be set up to just use the credentials of whoever is logged in.

Defines the login name that the system will use when sending Triggers.

Defines the password that the system will use when sending Triggers.

Defines the web address/name for the specified "Trigger Username" and "Trigger Password".

Defines the Application ID which is supplied by Microsoft when companies register their application, Deacom in this instance, with their Office365 account.

Defines the Tenant ID passwords which is supplied by Microsoft when companies register their application, Deacom in this instance, with their Office365 account.